
File name: README_1.2.5.1.txt
****************************************************************
|                                                              |
|  Nortel Networks Layer 2/3 GbE Switch Module (GbESM) for     |
|  IBM eServer BladeCenter Firmware Update                     |
|                                                              |
|  Revision/Build ID: 1.2.5.1                                  |
|                                                              |
|  (C) Copyright International Business Machines Corporation   |
|      December, 2005. All rights reserved.                    |
|                                                              |
|  US Government Users Restricted Rights -- Use, duplication   |
|  or disclosure restricted by GSA ADP Schedule Contract with  |
|  IBM Corp.                                                   |
|                                                              |
|  Note: Before using this information and the product it      |
|  supports, read the general information under "NOTICES AND   |
|  TRADEMARKS" in this document.                               |
|                                                              |
|  Updated < 07 March 2007 >                                   |
****************************************************************

CONTENTS
________

1.0  Overview
2.0  Change history
3.0  Installation and setup instructions
  3.1  Software update procedure
  3.1.1  Using Telnet
  3.1.2  Using BBI
  3.2  How to check the firmware version
4.0  Configuration information
5.0  Unattended Mode
6.0  Web information and support phone number
  6.1  Web sites
  6.2  Software service and support
  6.3  Hardware service and support 
7.0  Notices and trademarks
8.0  Disclaimer
  8.1  Document provision
  8.2  Note to government users


1.0 Overview
____________

This file is intended for network administrators responsible for
upgrading the firmware for the Nortel Networks Layer 2/3 Gigabit
Ethernet Switch Module (GbESM).

For a summary of GbESM features, supplemental information and 
known issues associated with this release, please refer to the 
"Release Notes - Layer 2-3 GbE Switch Module for IBM eServer
BladeCenter", available via web sites indicated in section 6.1.



2.0 CHANGE HISTORY
__________________

Version 1.2.5.1 (Released March 2007)

 Enhancements:	

- Added support for the new  daylight savings time rules for NTP (Network
  Time Protocol). Starting in 2007, daylight savings time will begin
  at 2AM on the second Sunday in March and end at 2AM on the first Sunday
  in November.  The new change can be configured through AOS (Alteon 
  Operating System) CLI (Command Line Interface) only.

- Changed the default configuration to enabled autonegotiation on internal
  ports. This makes it possible to flow control on internal blade ports. 

Note: 

  For the port mirroring enhancement added in Version 1.2.4.1 (number 7620),
  the caution regarding its use still applies.  See the Version 1.2.4.1
  change history below for the details.

 Fixes:
 
- Corrected a condition where the switch would panic when a configuration was 
  applied over SNMP (Simple Network management Protocol) while revert applying
  on the CLI (Command Line Interface). (fix number 10623)

- Corrected a condition where the switch would panic when reverting a 
  configuration over SNMP while applying a configuration on the CLI.
    (fix number 10624)

- Corrected a condition where Layer-3 information was dumped twice by the 
  Information Dump command.   IP (Internet Protocol) information was 
  repeated twice in the tsdump (technical support dump).
    (fix number 10734)

- Now includes the save of MP (management processor) stack backtrace in the
  panic dump file.  The change does not affect the running switch code, it
  only executes once the switch has crashed and is in crash information
  collection mode, before the reboot.  (fix number 11437)

- Fixed IGMP (Internet Group Management Protocol) processing for certain 
  conditions causing IGMP responses to return as a tagged 802.1Q frame when
  tagging is disabled.      (fix number 11775)

- Corrected a condition where LACP (Link Aggregation Control Protocol) system
  priority changes occurred without entering a value.   
  Typing "/c/l2/lacp/sysprio" command would change the value even when no 
  value was entered.        (fix number 11364)  

- Corrected a condition where one tagged BPDU was sent after a topology change,
  on an untagged port.      (fix number 11825)



Version 1.2.4.1 (Released September 2006)

 Enhancements:

 Fixes:

The following fixes are all corrections to the SNMP interface to the switch.
They are provided to prepare for the support for an upcoming release of 
BLADE HARMONY.


- Corrected a condition where a SNMP user cannot configure number of
  COS queue using the “Numcos” option  (fix number 9264)

- Corrected a condition where an invalid default gateway 
  with IP address 0.0.0.0 can be entered  (fix number 8942)

- Corrected a condition where the switch display wrong value for the 
  “Total Learned Discard” parameter after the switch is reset to 
  factory default configuration.  (fix number 8915)

- Corrected a condition where BLADE HARMONY does not show the 
  “RMON” and “SERVER” options from the “Syslog-Trap” tab.
    (fix number 8889)

- Corrected a condition where a new interface can be assigned to
  a non existing VLAN  (fix number 8820)

- Corrected a condition where a switch module cannot add trunk groups
  to “Fail over Trigger”  (fix number 8876) 

- Corrected a condition where a switch module cannot set VLAN 
  state from on to off during a fail over  (fix number 8774)

- Corrected a condition where an internal port after being excluded 
  from the management VLAN cannot be added back to the management VLAN
    (fix number 8770)

- Corrected a condition where the switch module crashes when modifying 
  the IP mask of a duplicate entry on the Management Network tab 
   (fix number 8730)

- Corrected a condition where the switch module shows inconsistent port
  mirroring  (fix number 8786) 


Version 1.2.4.0 (Released September 2006)


 Enhancements:	

- Changed the "default" configuration for QOS queues from 8 queues
  to 2 queues.

  This change will minimize exposure to performance
  issues associated with iSCSI applications.  The memory space for 
  QOS traffic queues is fix.  Select the number of queues to  
  satisfy traffic requirements.  Fewer queues will provide great
  memory storage space per queue. (number 21765)

- Added a new configuration menu: /cfg/l2/fdb
 
  This menu provides 3 basic features:
 
	1.       learn enable|disable
 
	The learn feature will control if the switch learns a MAC address
        in the forwarding database.  If the MAC is learned it will be 
        displayed in the /info/l2/fdb/dump output.  Once a MAC is learned
        in the FDB it will no longer be flooded out to all ports. 
        Learning is enabled by default
 
	With learning disabled, all packets will be flooded.
 
	2.       flood enable|disable
 
	The flood feature controls whether unknown MAC addresses will be
	flooded to all ports.  If this feature is off and the MAC address
        is not learned in the FDB, then the packet will not be forwarded
        to the destination ports.  By default, flood is enabled.
        If flooding is disabled, the MAC address must be statically entered
        with the following commands.
 
	3.       static
 
	The static command is a menu used for entering Static MAC Addresses.
        This menu has the commands:
 
	add - Add a permanent FDB entry
	del - Delete a static FDB entry
	clear - Clear static FDB entries
	cur - Display current static FDB configuration
                                                                                 
  There is also a new information command /info/sys/chassis used to display
  important chassis related state information.  
 

- For Certain port mirroring configurations in which multiple mirror ports 
  are used, disabling L2 learning control on the switch allows the 
  mirrored traffic to be sent to multiple mirror ports or member of 
  VLANs that are configured to the mirror port(s). (number 7620)

*** CAUTION ***

  A caution is provided regarding the use of this new enhancement.
  The firmware currently does not prohibit the user from configuring
  an invalid combinations of options.   For example,

  With 1.2.4.0, the switch will still do flooding when you have the 
  following combination configured:
 
	/c/l2/fdb/learn ena
	/c/l2/fdb/flood dis

  Future firmware release 1.3.0 will provide a check which will prohibit 
  the user from selecting this configuration.   Until the firmware is made
  available, the user is cautioned to exercise extra care in using this 
  function.

 Fixes:

- Corrected a condition where a configuration cannot be saved when a 
  user configure intergap extension (/maint/sys/ipgen). 
  (fix number 7868)

- Corrected a condition where the IBM Management Module (MM) may
  receive duplicate acknowledgements to the push of an IP address
  on the reboot of the switch.   The second response was intrepreted 
  by the MM as an unsolicited IP change, thus causing the MM to 
  clear the switch IP resulting in a drop of the connection to the 
  switch.  This fix checks the extended control register on the 
  switch module (IPCfgFromVPD) before signaling the MM that the
  switch POST is complete, and switch is ready to receive the IP
  address. This fix may lengthen the diagnostic completion time 
  for the switch.  (fix number 8964)

- Corrected a condition where the GbESM SNMP MIB (aosacl.mib)
  generates syntax errors when used in conjunction with HP OpenView.
  (fix number 7503)

- Corrected a condition where in some cases, some SNMP operation
  will attempt to grab a same semaphore twice which cause the 
  switch to panic. (fix number 7897)

- Corrected a condition when a user boots the switch from factory
  default setting, use SNMP or BBI to configure the switch and save
  the configuration into the active configuration.  After reboot, 
  the switch still use factory default setting (this condition does 
  not happen when the user performs all steps using the cli)
  (fix number 8761)

- Corrected a condition where in some cases the switch information 
  dump (uudump) file generated by the switch is corrupted.
  (fix number 7808)

- Corrected a condition when a configuration for port mirroring 
  was not saved after the save command was issued and the switch 
  is rebooted. (fix number 7994)

- Corrected a condition where the user cannot change port setting 
  configuration using SNMP v3 (the change operates normally using 
  the command line interface – CLI) (fix number 7605, 7606)


Version 1.2.3.11 (GA Candidate May 02, 2006)

 Enhancements:  none 
	
 Fixes:
 
 Two localized minor code changes were made to 1.2.3.10.
 One corrects issues BBI operations, and the second corrects
 a condition encountered FTPing invalid images to the switch.

 BLADE Quality Engineering states that the code changes are
 minor and isolated and the exposure of introducing any 
 operational issues is very small.

 BLADE also identified that the BBI defect was not limited 
 to port control.

CMVC 324137  Sev  3
Abstract    BIOP/SV: BBI config switch port state not working

CMVC 322811  Sev 2
Abstract    BIOP/SV: Telnet session hangs downloading invalid image

CMVC 322849   Sev 2  
Abstract    BIOP/SV: Fin_wait2 created for invalid download attempt


Version 1.2.3.10 (GA Candidate April 14, 2006)

 Enhancements:
	
 - BladeSymphony, which provides a graphical user interface
   supporting remote management of the GbESM through SNMP has
   been introduced in conjunction with this release. 

   Refer to the "Using BladeSymphony 1.0" document for details.

 Fixes:

 - (IBM Global Systems reported problem) Tagged BPDU's were being
    transmitted on ports that did not have tagging enabled.  This
   caused Cisco switches connected upstream to not enable ports
    with VLAN configured, and PVST and trunk disabled.  

   With a VLAN STG other than 1, and that being the only VLAN on the
   port, the switch would transmit tagged BPDUs.  This has been 
   corrected.   The L2-3 GbESM never transmit tagged BPDUs on
   a port that does not have tagging enabled.  (BLADE BUG 4702)

 - (Turbine reported problem) RTSP in FWD state causing an LACP loop
    and all data packets dropped.  
   
   On a reboot, both ports at layer 2 physical interfaces forward and 
   both believe they are the root port for spanning tree, thus the 
   connection is dropped.  LAG may be up but physical interfaces
   are dormant.  (BLADE BUG 6307)

 - (IBM CMVC 304017) /info/log Log does not record time/date changes
   from the BBI.  (BLADE BUG 5402)

 - Tighten the restriction that prevent a user from upgrading with 
   a firmware file of similar content to a valid file but intended
   for a different switch type.  (BLADE BUG 4702)

 - (Related BLADE BUG 4402) FTPing an invalid image initially posts
    a message saying image is invalid, but then the message times out
    and the CLI returns.  

 - NNCLI ssh ON/OFF configuration not working.
   Command worked in OS mode but not NNCLI.  (BLADE BUG 5821)

 - With the BBI, if a Management Network and Mask such as 
   10.0.0.0, 255.0.0.0, is changed to all zeros, the subnet
   mask remains unchanged.  CLI works OK.  (BLADE BUG 4782)


Version 1.2.2.0 (Released January 31, 2006)

 Fix: 

 - Fixed flooding for unregistered multicast packets,
   and for IGMP snooping disabled VLANs. 


Version 1.2.1.0 (Release January 2006)

 Enhancements:
 - Added "industry standard" CLI (NNCLI) mode 


Version 1.1.1.1 (Released October 2005)

 Fixes:
 - General IGMP cleanup

 Enhancements:
 - L2 Trunk Failover improvements (VLAN-based, static or LACP trunks,
   more trigger options)
 - Number of allowable trunk groups increased to 13
 - Support for trunking INT ports from same blade
 - Available Spanning Tree Groups increased to 32
 - Maximum VLANs supported increased to 1024
 - Management feature improvements (logging/alarm/alert suppression)
 - Software upgrade via HTTP (i.e. browser)
 - Support end-to-end Flow Control using 802.3 Pause Frame protocol
 - Ability to tag Native VLAN (PVID) traffic


Version 1.0.1.6 (Released June 2005)

 Fixes:

 - No tagged PVST BPDUs in the native vlan if associated STP is off
 - Tagged BPDU's not being forwarded
 - IGMP becomes non-functioning after reboot
 - Inaccurate link values/states returned via SNMP
 - Forwarding Data Base (FDB) not flushed when last link in trunk
   goes down
 - Ports transitioning from STP Forwarding to Blocked states are not
   flushed from the IGMP table
 - Cannot delete a static Multicast Router port
 - CLI misreporting high MP utilization
 - Changing link type in BBI not reflected in CLI
 - Virtual Router GUI not posting VRs correctly in BBI DASHBOARD mode


Version 1.0.1.1 (January 2005)
 - Initial Release.



3.0 INSTALLATION AND SETUP INSTRUCTIONS
_______________________________________

The GbESM firmware is comprised of two (2) code images.  The boot
code and a switch operating system.  The GbE switch module ships
with this firmware pre-installed. However, new versions of the
firmware are periodically released and can be used to update the
features and function of the switch.


 3.1 Software update procedure
 -----------------------------

 Update the switch software using a TFTP or FTP server
 application. Typically, this application is installed on a
 machine that is reachable from the switch through the external
 ports or the management module.

 NOTES:
     - The following steps reflect the use of a TFTP server.
       A FTP server can also be used.

     - Upgrades can also be performed using external ports. Please
       see "Externally managing the GbE switch module" in the
       GbESM Installation Guide.

 1) Download the GbESM software package (zip file) to the machine
    where the TFTP server resides.

 2) Extract the Boot and OS image files into a directory. Enable
    the server and set its default directory to the one where the
    image files reside.

 3) Establish a connection between the ethernet port of the
    BladeCenter Management Module and the TFTP Server.

 4) Using the Management Module web interface (GUI), configure the
    IP Addr/Mask of the Management Module External (eth0) and
    Internal (eth1) interfaces, the GbESM switch and the TFTP server
    so that they all reside on the same subnet.

    For example,

        Management Module (eth0) => 192.168.70.125 / 255.255.255.0

        Management Module (eth1) => 192.168.70.126 / 255.255.255.0

        GbESM Current IP Config  => 192.168.70.127 / 255.255.255.0

        TFTP Server              => 192.168.70.254 / 255.255.255.0

     NOTE: Although configured as such, for this example, the 
           TFTP Server does not have to be on the same subnet as
           long as a proper gateway address is configured in the
           switch.


 3.1.1 Using Telnet
 ------------------

 1) Using the Management Module GUI, navigate to:

    I/O Module Tasks -> Configuration -> Bay X ->
               Advanced Configuration -> Start Telnet session
    
    When the telnet session is established, you will begin using
    the Command Line Interface (CLI) of the GbE switch.

 2) Enter "admin" for the password.

    The GbE switch provides storage for two (2) OS images and
    one (1) Boot image. What you are about to do consists of the
    following sequence:

     - load the new OS image into one of the image banks
     - reset the switch
     - load the Boot image
     - reset the switch

     NOTE: When you reset the switch it boots using the 'selected'
           image (1 or 2). Please ensure that you are booting from
           the upgraded image (execute /boot/cur to determine).

 3) Upgrade the OS image by entering the following commands:

    a) /boot/gtimg X TADDR GbESM-AOS-1.2.5.1_OS.img

       WHERE:
       ------
           X  => 1 or 2 (depends which image bank you want to use)
       TADDR  => IP Address of the TFTP Server
 
       NOTE: It is recommended that you retain the previous OS
             version by loading the upgrade into the other image
             bank and then reset the switch using the new image.
             (use /boot/image command to select preferred image)

       Answer 'Y' to the confirmation question, then wait for the 
       upgrade to complete successfully.
 
    b) /boot/reset

       NOTE: You MUST Reset the switch to activate the new image.
             Resetting the switch kicks you out of the CLI, so
             Steps 1 and 2 need to be executed again before
             proceeding to the next step.
             A switch reset completes in approximately 60 seconds.

 4) Upgrade the Boot image by entering the following commands:

    a) /boot/gtimg boot TADDR GbESM-AOS-1.2.5.1_Boot.img

       Answer 'Y' to the confirmation question, then wait for the 
       upgrade to complete successfully.

    b) /boot/reset


 3.1.2 Using BBI
 ---------------

 1) Using the Management Module GUI, navigate to:

    I/O Module Tasks -> Configuration -> Bay X ->
               Advanced Configuration -> Start Web session
    
 2) Enter "admin" for the username and 'admin' for the password.

 3) Click the CONFIGURE button (near top of page)

 4) In the frame on the left, click on the "Nortel Networks
    Layer 2-3 GbE" folder icon and navigate to:

    System -> Config/Image Control

    The GbE switch provides storage for two (2) OS images and
    one (1) Boot image. What you are about to do consists of the
    following sequence:

     - load the new OS image into one of the image banks
     - reset the switch
     - load the Boot image
     - reset the switch

     NOTE: When you reset the switch it boots using the 'selected'
           image (1 or 2). Please ensure that you are booting from
           the upgraded image (see "Next Boot Image Selection" field).

 5) Upgrade the OS image as follows:

    a) Fill in the following three (3) fields on the lower half of
       the page:

       Hostname or IP Address of FTP/TFTP server => <server_addr>
       Image Filename => GbESM-AOS-1.2.5.1_OS.img
       Image for Transfer => 1 or 2 (i.e. the preferred image bank)

       NOTE: It is recommended that you retain the previous OS
             version by loading the upgrade into the other image
             bank and then reset the switch using the new image.
             (use the "Next Boot Image Selection" field to select
             the preferred image).

    b) Click the "Get Image" button.

       Wait for the upgrade to complete successfully.

    c) Click the "REBOOT!" button to reset the switch.
                                                        
       NOTE: You MUST Reset the switch to activate the new image.
             Resetting the switch kicks you out of the BBI, so
             Steps 1-4 need to be executed again before proceeding
             to the next step.
             A switch reset completes in approximately 60 seconds.

 6) Upgrade the Boot image as follows:

    a) Fill in the following three (3) fields on the lower half of
       the page:

       Hostname or IP Address of FTP/TFTP server => <server_addr>
       Image Filename => GbESM-AOS-1.2.5.1_Boot.img
       Image for Transfer => boot

    b) Click the "Get Image" button.

       Wait for the upgrade to complete successfully.

    c) Click the "REBOOT!" button to reset the switch.
                                                        

 3.2 How to check the firmware version
 -------------------------------------

 To check the version of the firmware images installed on the GbESM,
 use either of the following methods:

    a) From the CLI, execute the command:

       /boot/cur

       This command displays:

       Currently set to boot software image1, active config block.
       Current FLASH software:
         image1: version 1.2.5.1
         image2: version 1.2.4.1
         boot kernel: version 1.2.5.1
       Currently scheduled reboot time: none

    b) Using the Management Module GUI, navigate to:
    
         Monitors -> Firmware VPD

       Scroll down to view the VPD info for the appropriate GbE Switch.
       You should see the following entries:


      FIRMWARE TYPE             BUILD ID   RELEASED    REVISION
      -------------             --------   --------    --------

      Boot ROM                  WMZ05001   02/15/2007    0102  
      Main Application 1(or 2)  WMZ05001   02/15/2007    0102 

    
    The four digits comprising the version (e.g. 1.2.5.1) correlate
    to the REVISION/BUILD ID as follows:

      - Revision => 01 02  ... the first 2 digits of the version
      - Build ID => 05 001 ... the last 2 digits of the version


4.0 CONFIGURATION INFORMATION
_____________________________

For detailed switch configuration, please refer to,
"Command Reference - Layer 2-3 GbE Switch Module for IBM eServer
 BladeCenter", available via web sites indicated in section 6.1.


5.0 UNATTENDED MODE
___________________

Unattended Mode is not supported for updating the Nortel Switch
Module firmware.



6.0 Web information and support phone number
____________________________________________

If you have any questions about this update, or problems applying the 
    update, go to the following Help Center World Telephone Numbers
    and URL: http://www.pc.ibm.com/qtechinfo/YAST-3P2QYL.html.

Information and assistance is available through the IBM Web site
and by phone.


 6.1 Web sites
 -------------

 IBM Support Web Site:  http://www.ibm.com/pc/support/

 IBM eServer Web site:  http://www.ibm.com/eserver/xseries/


 6.2 Software service and support
 --------------------------------

 Through the IBM Support Line, you can get telephone assistance,
 for a fee, with usage, configuration, and software problems with
 xSeries servers. For information about which products are supported
 by Support Line in your country or region, go to
 http://www.ibm.com/services/sl/products/.

 For more information about Support Line and other IBM services, go to
 http://www.ibm.com/services/

 For support telephone numbers go to
 http://www.ibm.com/planetwide/

 In the U.S. and Canada, call 1-800-IBM-SERV (1-800-426-7378).


 6.3 Hardware service and support
 --------------------------------

 You can receive hardware service through IBM Services or through
 your IBM  reseller, if your reseller is authorized by IBM to
 provide warranty service.

 See http://www.ibm.com/planetwide/ for support telephone numbers, 
 or in the U.S.and Canada, call 1-800-IBM-SERV (1-800-426-7378).

 In the U.S. and Canada, hardware service and support is available 24 hours
 a day, 7 days a week. In the U.K., these services are  available Monday
 through Friday, from 9 a.m. to 6 p.m.                    


7.0 Notices and trademarks
__________________________


The following terms are trademarks of International Business
Machines Corporation in the United States, other countries, or
both:

e-business logo
eServer
IBM
xseries
BladeCenter

The following terms are trademarks of Nortel Networks in the 
United States, other countries, or both:

Nortel
Nortel Networks


8.0 DISCLAIMER
______________

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE. Some jurisdictions do not allow disclaimer of express or
implied warranties in certain transactions, therefore, this
statement may not apply to you.

This information could include technical inaccuracies or
typographical errors. Changes are periodically made to the
information herein; these changes will be incorporated in new
editions of the publication. IBM may make improvements and/or
changes in the product(s) and/or the program(s) described in this
publication at any time without notice. 


 8.1 Document provision
 ----------------------

 THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF
 ANY KIND.   IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS
 OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE IMPLIED
 WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE AND
 MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS
 DOCUMENT.   BY FURNISHING THIS DOCUMENT, IBM GRANTS NO
 LICENSES TO ANY PATENTS OR COPYRIGHTS.


 8.2 Note to government users
 ----------------------------

 Note to U.S. Government Users -- Documentation related to
 restricted rights -- Use, duplication or disclosure is
 subject to restrictions set forth in GSA ADP Schedule
 Contract with IBM Corporation.